Skip to main content
TrustRadius
Amazon CloudWatch

Amazon CloudWatch

Overview

What is Amazon CloudWatch?

Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.

Read more
Recent Reviews

A must-have!

9 out of 10
October 23, 2019
We use AWS to sync a lot of files that all the users need. It's a very good tool to keep track of everything, including notifications and …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing

Canaries

$0.0012

On Premise
per canary run

Logs - Analyze (Logs Insights queries)

$0.005

On Premise
per GB of data scanned

Over 1,000,000 Metrics

$0.02

On Premise
per month

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://aws.amazon.com/cloudwatch/prici…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

AWS Container Day - Amazon Cloudwatch (Container Insights)

YouTube
Return to navigation

Product Details

What is Amazon CloudWatch?

Amazon CloudWatch is a native AWS monitoring and observability service built for DevOps engineers, developers, site reliability engineers (SREs), and IT managers. CloudWatch provides users with data and actionable insights to monitor applications, respond to system-wide performance changes, optimize resource utilization, and get a unified view of operational health. CloudWatch collects monitoring and operational data in the form of logs, metrics, and events, providing users with a unified view of AWS resources, applications, and services that run on AWS and on-premises servers. CloudWatch can be used to detect anomalous behavior in environments, set alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep your applications running smoothly. With Amazon CloudWatch, there is no up-front commitment or minimum fee; users simply pay for what they use.

Amazon CloudWatch Screenshots

Screenshot of How Amazon CloudWatch works - high-level overviewScreenshot of CloudWatch Application MonitoringScreenshot of CloudWatch ServiceLens and Contributor Insights - expedite resolution timeScreenshot of Improve Observability with Amazon CloudWatchScreenshot of Visual overview of Amazon CloudWatch

Amazon CloudWatch Videos

Amazon CloudWatch: Complete Visibility of Your Cloud Resources and Applications
Governance with AWS

Amazon CloudWatch Competitors

Amazon CloudWatch Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo
Supported CountriesAmericas, Europe, Middle East, Africa, Asia Pacific

Frequently Asked Questions

Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.

Datadog, Azure Monitor, and Splunk IT Essentials are common alternatives for Amazon CloudWatch.

Reviewers rate Support Rating highest, with a score of 8.4.

The most common users of Amazon CloudWatch are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(167)

Attribute Ratings

Reviews

(1-6 of 6)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use Cloudwatch to see our EC2 instances and other AWS resources (like LoadBalancer, Elasticache, RDS, etc.). We designed custom dashboards for monitoring our performance and response time. You can create a particular alert with Cloudwatch alarms, and you can see your logs in Cloudwatch logs.
  • Stability and availability
  • Easy usage
  • Integration with other AWS Resources
  • Price is higher than other 3rd party monitoring tools and log shipping tools.
  • You can see 5-minute log intervals with standard monitoring.
You shouldn't use it if your log IO is so much. If your all-Cloud structure is AWS, you should use Cloudwatch.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
I used Amazon CloudWatch to monitor specific events in the AWS cloud. Out of the box CloudWatch provides events to monitor, but it also allows you configure other specific events through a UI selection screen. We created a group of events to monitor autoscaling events such as launches, terminations and changes. Also setup to monitor API calls to monitor thresholds, volumes and usage. This monitoring allowed us to determine if the application was up/down/stressed so that we could take action or cause activities to occur like launching additional instances.
  • Monitoring application state - up/down/stressed.
  • View of API calls - threshold, volumes, response times.
  • Rules-based functionality to allow for automatic triggering of Lambda functionality.
  • CloudWatch doesn't monitor things outside of the cloud, it's not what it is intended for.
  • Billing is confusing as it bills on Dashboard, metrics called, custom metrics, etc. Hard to forecast the charge.
  • Paradigm is confusing sometimes and difficult to learn.
It does very well for monitoring internal metrics of AWS. For instance monitoring API calls, instance starts/stops, and resource usage. Other third-party tools that sit on top of AWS are often better than CloudWatch when you are trying to analyze results. The system doesn't provide automatic analysis to guide you through the process or point out things you aren't monitoring for.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use CloudWatch to monitor logs of cloud services and other infrastructure. Mostly being used by our development and engineering departments. It gives us a good idea about the health of infrastructure and helps us prioritize maintenance activities.
  • Easy integration with other services.
  • Seamless Configuration.
  • Variety of matrix, graphs and dashboards.
  • Support to third party libraries.
  • User Interface can be improved.
  • High cost of implementation.
  • No Phone notifications.
It is a great tool for infrastructure monitoring. Very beneficial to monitor any web or cloud services.
Rob Bates | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use CloudWatch to monitor all of our cloud estates. We also integrate Cloudwatch into our main monitoring platform (SolarWinds) which allows us to pull the CloudWatch metrics down into SolarWinds. This is used specifically by our IT department, and our devs tend to use the native dashboard with CloudWatch. Overall it gives us visibility into our instances running in AWS and also provides us with alerting, which we also integrate into Slack.
  • Allows integration into non-native products (SolarWinds, Nagios, etc).
  • Proactive monitoring and recommendations.
  • Alerting and dashboards.
  • There is only a limited amount of credits available each month when pulling metrics into other applications. We have had to use larger polling intervals as a result.
  • Unable to export alert data into 3rd party data warehouses for record keeping.
  • Learning curve is slightly steep and there isn't much automation in terms of setting alerts up.
If you have a large cloud estate and need proactive monitoring, dashboards, and alerting then it makes sense to use CloudWatch as its obviously native to AWS. CloudWatch is well suited to anyone that wants to see into their data, their traffic, or their system health. It's the eyes and ears of AWS. It really is best for any scenario where you are hosting infrastructure with AWS and want to keep an eye on it.
Kyle Reichelt | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon Cloudwatch in a variety of ways, from monitoring the performance and validation success/failures of our ETL (extract, transform, and load) processes, our Lambda Services, our EC2 instances, our RDS instances, as well as our Redshift instance. Certainly we're using Amazon Cloudwatch to monitor day-to-day server-side activities, but the really impressive capabilities lie in its ability to both diagnose issue, as well as to trigger automated remediation.
  • Lambda process monitoring, particularly useful when you're relying on third-party services.
  • Active monitoring RDS (set thresholds so we know before a database runs out of space)
  • Auto-requisitioning of additional resources
Well suited if:
  • Your organization is married to the AWS ecosystem
  • You tech stack is reliant on third-party services
  • You use Splunk as your log aggregator (integrates well)
  • You prefer to be proactive about health of your tech stack
Not particularly suited if:
  • You don't use AWS
  • You like to fly by the seat of your pants
Brian Dentino | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon CloudWatch to aggregate and retain logs across all of the different services that make up our infrastructure. It is primarily used across our engineering and dev ops departments. Using CloudWatch logs allows us to address compliance issues associated with log retention because it is very easy to configure an expiration (if any) for log files. We also use CloudWatch metrics to monitor important KPIs and performance metrics for our business.
  • Managing log retention periods is very simple with CloudWatch, and can be configured on a per-group basis.
  • Monitoring host performance is very easy when coupled with the CloudWatch Agent on an EC2 instance. A simple installation and configuration replaces an entire 3rd-party host monitoring stack.
  • CloudWatch is flexible enough for not just host monitoring, but application monitoring as well. It's easy to pipe local logs up to CloudWatch and extract structured data in order to monitor and set alerts on custom app metrics.
  • Unfortunately, the CloudWatch dashboard does not provide the ability to create histograms of discrete counts. This makes it difficult to, for instance, use CloudWatch to quickly identify specific IP addresses that have a high request volume in a certain period.
  • The UX for creating a custom metric from a CloudWatch log group is somewhat confusing. Every time I need to create a new metric I find myself fumbling around the interface for a few minutes while I try to remember how to do it.
  • The alerting options for CloudWatch are not as extensive as are available with some 3rd-party services.
It is well suited for organizations already using a number of Amazon services, as most of these will integrate very nicely with CloudWatch. If you have detailed log retention requirements, it's quite nice as well since they make it easy to configure retention and export data to S3. The tooling for metric filters and dashboards are very customizable and sufficient for general monitoring but the UX is not the most friendly. If your organization spends a lot of time on business intelligence and performance tracking, you may want to consider a more targeted 3rd-party service.
Return to navigation